Internet Info 1994 March

home *** CD-ROM | disk | FTP | other *** search

/ Internet Info 1994 March / Internet Info CD-ROM (Walnut Creek) (March 1994).iso / inet / internet-drafts / draft-ietf-snanau-snamib-00.txt < prev next >

Wrap

Text File | 1993-08-02 | 90KB | 2,895 lines

Internet Draft SNANAU MIB July 30, 1993 Definitions of Managed Objects for SNA NAUs July 30 1993 Zbigniew Kielczewski (editor) Eicon Technology Corporation 2196 32nd Avenue Montreal, Quebec, Canada H8T 3H7 zbig@eicon.qc.ca Kitty Shih (editor) Novell 890 Ross Drive Sunnyvale, CA 94089 kmshih@novell.com 1. Status of this Memo This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a "working draft" or "work in progress." Please check the I-D abstract listing contained in each Internet Draft directory to learn the current status of this or any other Internet Draft. Expires January 1994 [Page 1] Internet Draft SNANAU MIB July 30, 1993 2. Abstract This Internet-Draft defines an extension to the Management Information Base (MIB) for use with SNMP-based network management. In particular, it defines objects for managing the configuration, monitoring and control of Physical Units (PUs) and Logical Units (LUs) in an SNA environment. PUs and LUs are two types of Network Addressable Units (NAUs) in the logical structure of an SNA network. NAUs are the origination or destination points for SNA data streams. This draft identifies managed objects for SNA Node Type 2.0 and LUs 0, 1, 2, 3. This memo does not specify a standard for the Internet community. Expires January 1994 [Page 2] Internet Draft SNANAU MIB July 30, 1993 3. The Network Management Framework The Internet-standard Network Management Framework consists of three components. They are: RFC 1155 which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. RFC 1212 defines a more concise description mechanism, which is wholly consistent with the SMI. RFC 1156 which defines MIB-I, the core set of managed objects for the Internet suite of protocols. RFC 1213, defines MIB-II, an evolution of MIB-I based on implementation experience and new operational requirements. RFC 1157 which defines the SNMP, the protocol used for network access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. This draft uses the SNMPv1 Framework; later drafts will reflect the SNMPv2 framework. Expires January 1994 [Page 3] Internet Draft SNANAU MIB July 30, 1993 4. Objects Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) [7] defined in the SMI. In particular, each object has a name, a syntax, and an encoding. The name is an object identifier, an administratively assigned name, which specifies an object type. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the OBJECT DESCRIPTOR, to also refer to the object type. The syntax of an object type defines the abstract data structure corresponding to that object type. The ASN.1 language is used for this purpose. However, the SMI [3] purposely restricts the ASN.1 constructs which may be used. These restrictions are explicitly made for simplicity. The encoding of an object type is simply how that object type is represented using the object type's syntax. Implicitly tied to the notion of an object type's syntax and encoding is how the object type is represented when being transmitted on the network. The SMI specifies the use of the basic encoding rules of ASN.1 [8], subject to the additional requirements imposed by the SNMP. 4.1. Format of Definitions Section 6 contains contains the specification of all object types contained in this MIB module. The object types are defined using the conventions defined in the SMI, as amended by the extensions specified in RFC1212 [9]. Expires January 1994 [Page 4] Internet Draft SNANAU MIB July 30, 1993 5. Overview This draft identifies the proposed set of objects for managing the configuration, monitoring and control of Physical Units (PUs) and Logical Units (LUs) in an SNA environment. Note that this draft uses "PU" to describe SNA Node Type 2.0, and "LU" to describe Logical Units of Type 0, 1, 2, and 3. PUs and LUs are two types of Network Addressable Units (NAUs) in the logical structure of an SNA network; NAUs are the origination or destination points for SNA data streams. Highlights of the mib include: - Objects that reflect the state of PUs and the LUs as well as statistical information on PUs and LUs. - Objects that support control functions such as starting and stopping PUs, and terminating LU sessions. In addition, traps are defined to indicate PU and LU state changes. 5.1. Applying MIB II to managing SNA NAUs This section will identify how MIB II objects, specifically the MIB II system and interfaces group will be used in SNMP- based management of SNA NAUs. The following describes the use of the sysUpTime object from the MIB II system group: sysUpTime: clock in the SNMP agent/proxy-agent; expressed in TimeTicks (1/100s of a seconds). The timestamp value for an event in the SNA NAU MIB will be equal to the value of sysUpTime taken when the event takes place. The use of the other system group objects also follows standard SNMP practices. Use of the MIB II Interfaces Group is to be determined. Future drafts of the SNANAU mib will reflect the results of the if-mib working group. Expires January 1994 [Page 5] Internet Draft SNANAU MIB July 30, 1993 5.2. SNANAU MIB Structure The proposed SNANAU MIB module contains three groups of objects: snaPu20 - objects related to Node Type 2.0 configuration, monitoring and control. snaLu - objects related to LU 0, 1, 2, 3 definition, monitoring and control. snaMgtTools - objects related to specific management tools well known in SNA environments. These groups are described in the following sections. 5.2.1. SNA PU 2.0 (snaPu20) Group The snaPu20 group consists of the following tables: 1) snaPu20CfgTable Each row contains configuration description of one Node (type 2.0). The table structure allows row creation, modification and deletion. The table is indexed by Node ID (PositiveInteger). Each entry also contains a reference to a corresponding entry in one of following three link tables (802.2, SDLC or QLLC) which describes the underlying logical link implementation. 2) snaPu20Link802Dot2Table Each row contains configuration information for an 802.2 logical link used by an 2.0 Node. The table structure allows row creation, modification and deletion. It is indexed by Node ID (PositiveInteger). 3) snaPu20LinkSdlcTable Each row contains configuration information for an SDLC link used by an 2.0 Node. The table structure allows row creation, modification and deletion. It is indexed by Node ID (PositiveInteger). 4) snaPu20LinkQllcTable Each row contains configuration information for a QLLC link used by an 2.0 Node. The table structure allows row creation, modification and deletion. It is indexed by Node ID (PositiveInteger). Expires January 1994 [Page 6] Internet Draft SNANAU MIB July 30, 1993 5) snaPu20StateTable Each row contains runtime and state variables for a 2.0 Node. The table is indexed by Node ID (PositiveInteger). It is an extension of snaPu20CfgTable. The rows in this table are created by an Agent. 6) snaPu20StatsTable Each row contains statistics variables (counters) for a 2.0 Node. The table is indexed by Node ID (PositiveInteger). It is an extension of snaPu20CfgTable. The rows in this table are created by an Agent. 5.2.2. SNA LU (snaLu) Group The snaLu Group consists of the following tables: 1) snaLuCfgTable Each row contains definition parameters of one LU. Each row contains a reference to a 2.0 Node to which this LU belongs. The table is thus indexed by Node ID and LU ID. The table structure allows modifications. The rows in this table are created by an Agent. 2) snaLuStateTable Each row contains state variables of an LU. The table is indexed by Node ID and LU ID. It is an extension of snaLuCfgTable. The rows in this table are created by an Agent . 3) snaLuStatsTable Each row contains statistics variables (counters) of an LU. The table is indexed by Node ID and LU ID. It is an extension of snaLuCfgTable. The rows in this table are created by an Agent. 5.2.3. SNA Management Tools (snaMgtTools) Group This is an optional group. The snaMgtTools group consists of the following table: 1) snaLuRtmTable Each row contains NetView RTM variables of an LU. The table is indexed by Node ID and LU ID. It is an extension of snaLuCfgTable. The rows in this table are created by an Agent. More groups may be defined in the future to provide the compatibility with existing popular SNA management tools. Expires January 1994 [Page 7] Internet Draft SNANAU MIB July 30, 1993 6. Object Definitions SNA-NAU-MIB DEFINITIONS ::= BEGIN -- This is the 7/30/93 draft text of the SNANAU MIB. -- It reflects comments discussed -- during the Amsterdam IETF meeting in July. -- It also incorporates some comments received from the WG -- after the meeting. -- This draft contains objects necessary for management of -- SNA devices: PU 2.0 and LU 0, 1, 2, 3. -- Naming conventions in this document: -- -- The name 'SNA Gateway' or 'Gateway' is used always in this -- document as a synonym of the software subsystem which -- implements SNA Gateway function. -- The following objects apply to the management of SNA devices -- which form the basis of the Gateway implementation. -- The management of the Gateway itself is not in the scope of this -- document. -- Following names are used according to SNA conventions. -- The name 'PU' is used to describe Node Type 2.0 -- The name 'LU' is used to describe Logical Units of Type 0,1,2,3 -- Row creation: -- -- Many tables in this MIB allow the creation and deletion of -- rows. The method defined in RMON MIB is used to achieve this. -- The entry in the table which allows row creation has an object -- with syntax EntryStatus. -- The value 'invalid(4)' is used to delete the entry. -- Creation of an entry is done in the following way: -- A Management Station sets the object with syntax EntryStatus to th e -- 'createRequest(2)' value, using a random value for the instance in dex. -- This object may only be set to 'createRequest(2)' if this instance -- is created. If the set operation succeeds, then the Agent changes -- the value of the status object to 'underCreation(3)' and -- Management Station can set other (read-write) objects to -- complete the row creation. -- If the set operations are successful then Management -- Station changes the object with syntax EntryStatus to the value -- 'valid(1)', or else, it can abort using the value 'invalid(4)'. -- Proposed structure of the sna family of mibs: Expires January 1994 [Page 8] Internet Draft SNANAU MIB July 30, 1993 -- -- experimental -- sna -- snaNau - this draft -- snaDlc -- snaAppc -- snaGate -- snaAppn -- ... IMPORTS Counter, experimental, Gauge, TimeTicks FROM RFC1155-SMI DisplayString FROM RFC1213-MIB EntryStatus FROM RFC1271-MIB OBJECT-TYPE FROM RFC-1212 TRAP-TYPE FROM RFC-1215; -- NOTE: this assignment is only temporary sna OBJECT IDENTIFIER ::= { experimental 9999 } snaNau OBJECT IDENTIFIER ::= { sna 1 } snaPu20 OBJECT IDENTIFIER ::= { snaNau 1 } snaLu OBJECT IDENTIFIER ::= {snaNau 2 } snaMgtTools OBJECT IDENTIFIER ::= {snaNau 3 } -- Local textual conventions OperState ::= INTEGER { other (1), -- none of the following disabled (2), -- cannot operate for some reason enabled (3), -- in ready state but not operating active (4), -- ready and operating busy (5) -- operating but cannot accept more traffic } AdminState ::= INTEGER { other (1), start (2), stop (3) Expires January 1994 [Page 9] Internet Draft SNANAU MIB July 30, 1993 } PositiveInteger ::= INTEGER (1..65535) -- *************************************************************** -- snaPu20 group -- -- Implementation of the snaPu20 group is mandatory. -- -- It contains Managed Objects related to PU Type 2.0. -- *************************************************************** snaPu20CfgTable OBJECT-TYPE SYNTAX SEQUENCE OF SnaPu20CfgEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table contains all configuration parameters of PUs. The link specific parameters are contained in a row of a separate table referenced by snaPu20CfgLinkSpecific object. The entries in this table can be generated initially, after reboot, by the Agent which uses information from PU configuration file. Subsequent modifications of parameters, creation of new PUs entries and deletion of entries is possible. The modifications of this table can be saved in the PU configuration file for next reboot, but mechanism for this function is not defined here." ::= { snaPu20 1 } snaPu20CfgEntry OBJECT-TYPE SYNTAX SnaPu20CfgEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Entry contains all configuration parameters of one PU. The objects in the entry have read-write access. Entry can be created, modified or deleted. The object snaPu20CfgEntryStatus is used (set) to create or delete an entry. The object snaPu20CfgLinkSpecific can be set later, after the entry has been created." Expires January 1994 [Page 10] Internet Draft SNANAU MIB July 30, 1993 INDEX { snaPu20CfgIndex } ::= { snaPu20CfgTable 1 } SnaPu20CfgEntry ::= SEQUENCE { snaPu20CfgIndex PositiveInteger, snaPu20CfgName DisplayString, snaPu20CfgType INTEGER, snaPu20CfgId OCTET STRING, snaPu20CfgBlockId OCTET STRING, snaPu20CfgMaxPiu INTEGER, snaPu20CfgActivationMethod INTEGER, snaPu20CfgLuTermMethod INTEGER, snaPu20CfgNetId DisplayString, snaPu20CfgLinkType INTEGER, snaPu20CfgLinkSpecific OBJECT IDENTIFIER, snaPu20CfgEntryStatus EntryStatus } snaPu20CfgIndex OBJECT-TYPE SYNTAX PositiveInteger ACCESS read-only STATUS mandatory DESCRIPTION "Used to index the instances of objects. If Agent creates the entry then it will assign this number otherwise Management Station generates a random number when it reserves the entry for creation." ::= { snaPu20CfgEntry 1 } snaPu20CfgName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..8)) ACCESS read-write Expires January 1994 [Page 11] Internet Draft SNANAU MIB July 30, 1993 STATUS mandatory DESCRIPTION "The name of the PU which will be used during PU activation with SSCP." ::= { snaPu20CfgEntry 2 } snaPu20CfgType OBJECT-TYPE SYNTAX INTEGER { other(1), pu20(2) } ACCESS read-write STATUS mandatory DESCRIPTION "The type of PU." ::= { snaPu20CfgEntry 3 } snaPu20CfgId OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..2)) ACCESS read-write STATUS mandatory DESCRIPTION "The Node Id number of this PU as configured on VTAM and used during activation. Only first 12 bits are used." ::= { snaPu20CfgEntry 4 } snaPu20CfgBlockId OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..3)) ACCESS read-write STATUS mandatory DESCRIPTION "The Node block Id number of this PU as configured on VTAM and used during activation. Only first 20 bits are used." ::= { snaPu20CfgEntry 5 } snaPu20CfgMaxPiu OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "Maximum number of octets that can be exchanged by this PU in one Pathcontrol Information Unit (PIU)." Expires January 1994 [Page 12] Internet Draft SNANAU MIB July 30, 1993 ::= { snaPu20CfgEntry 6 } snaPu20CfgActivationMethod OBJECT-TYPE SYNTAX INTEGER { other (1), startup (2), demand (3) } ACCESS read-write STATUS mandatory DESCRIPTION "Indicates how the PU should be activated for the first time. The values have following meaning: startup (2) - at boot time (this is default) demand (3) - not at boot time but only when LU has to be activated. Any PU may be activated any time by Management Station request." ::= { snaPu20CfgEntry 7 } snaPu20CfgLuTermMethod OBJECT-TYPE SYNTAX INTEGER { other (1), unbind (2), termself (3), rshutd (4) } ACCESS read-write STATUS mandatory DESCRIPTION "Indicates how LUs of this PU should be deactivated. The values define which method has to be used." ::= { snaPu20CfgEntry 8 } snaPu20CfgNetId OBJECT-TYPE SYNTAX DisplayString (SIZE(0..8)) ACCESS read-write STATUS mandatory DESCRIPTION "The Network Id for this PU, it corresponds to NETID parameter in VTAM. Each PU in the Gateway can be attached to different SNA network." ::= { snaPu20CfgEntry 9 } Expires January 1994 [Page 13] Internet Draft SNANAU MIB July 30, 1993 snaPu20CfgLinkType OBJECT-TYPE SYNTAX INTEGER { other (1), link8022 (2), qllc (3), sdlc (4), channelAttach (5), tcpip (6) } ACCESS read-write STATUS mandatory DESCRIPTION "The type of link protocol used for this PU." ::= { snaPu20CfgEntry 10 } snaPu20CfgLinkSpecific OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-write STATUS mandatory DESCRIPTION "The row in a table specific for the link. It is the object identifier representing the instance of the index variable in one of the PU link tables from this MIB." ::= { snaPu20CfgEntry 11 } snaPu20CfgEntryStatus OBJECT-TYPE SYNTAX EntryStatus ACCESS read-write STATUS mandatory DESCRIPTION "Used by Management Station to create or delete the entry. The set request with the value 'createRequest(2)' will be successful only if the instance does not exist. When the entry is created this variable will change value to 'valid(1)'." ::= { snaPu20CfgEntry 12 } -- *************************************************************** -- The following table contains 802.2 specific configuration -- parameters. -- *************************************************************** Expires January 1994 [Page 14] Internet Draft SNANAU MIB July 30, 1993 snaPu20Link802Dot2CfgTable OBJECT-TYPE SYNTAX SEQUENCE OF SnaPu20Link802Dot2CfgEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table contains Managed Objects which describe basic configuration parameters for PUs using 802.2 link. The entries in this table can be generated initially, after reboot, by the Agent which uses information from PU configuration file. Subsequent modifications of parameters, creation of new PU link entries and deletion of entries is possible. The modifications of this table can be saved in the PU configuration file for next reboot, but mechanism for this function is not defined here." ::= { snaPu20 2 } snaPu20Link802Dot2CfgEntry OBJECT-TYPE SYNTAX SnaPu20Link802Dot2CfgEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Entry contains all link configuration parameters for one PU. The objects in the entry have read-write access. Entry can be created or deleted. The object snaPu20Link802Dot2CfgEntryStatus is used (set) to create or delete an entry." INDEX { snaPu20Link802Dot2CfgIndex } ::= { snaPu20Link802Dot2CfgTable 1 } SnaPu20Link802Dot2CfgEntry ::= SEQUENCE { snaPu20Link802Dot2CfgIndex PositiveInteger, snaPu20Link802Dot2CfgSourceAddress OCTET STRING, snaPu20Link802Dot2CfgSourceSAP INTEGER, snaPu20Link802Dot2CfgDestinationAddress OCTET STRING, snaPu20Link802Dot2CfgDestinationSAP INTEGER, snaPu20Link802Dot2CfgMediaType DisplayString, snaPu20Link802Dot2CfgAdapterType Expires January 1994 [Page 15] Internet Draft SNANAU MIB July 30, 1993 INTEGER, snaPu20Link802Dot2CfgAdapterName DisplayString } snaPu20Link802Dot2CfgIndex OBJECT-TYPE SYNTAX PositiveInteger ACCESS read-only STATUS mandatory DESCRIPTION "The index variable assigned by Agent for initial configuration read from file and by Management Station for subsequent entry creation." ::= { snaPu20Link802Dot2CfgEntry 1 } snaPu20Link802Dot2CfgSourceAddress OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..12)) ACCESS read-write STATUS mandatory DESCRIPTION "Medium Access Control (MAC) address of the source node of this logical link." ::= { snaPu20Link802Dot2CfgEntry 2 } snaPu20Link802Dot2CfgSourceSAP OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The source node's Service Access Point (SSAP)." ::= { snaPu20Link802Dot2CfgEntry 3 } snaPu20Link802Dot2CfgDestinationAddress OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..12)) ACCESS read-write STATUS mandatory DESCRIPTION "Medium Access Control (MAC) address of the destination node of this logical link." ::= { snaPu20Link802Dot2CfgEntry 4 } snaPu20Link802Dot2CfgDestinationSAP OBJECT-TYPE SYNTAX INTEGER Expires January 1994 [Page 16] Internet Draft SNANAU MIB July 30, 1993 ACCESS read-write STATUS mandatory DESCRIPTION "The Service Access Point used by the remote node (DSAP)." ::= { snaPu20Link802Dot2CfgEntry 5 } snaPu20Link802Dot2CfgMediaType OBJECT-TYPE SYNTAX DisplayString ACCESS read-write STATUS mandatory DESCRIPTION "The underlying physical media type: token-ring or ethernet." ::= { snaPu20Link802Dot2CfgEntry 6 } snaPu20Link802Dot2CfgAdapterType OBJECT-TYPE SYNTAX INTEGER { primary (1), secondary (2) } ACCESS read-write STATUS mandatory DESCRIPTION "Specific network adapter that is used for the 802.2 link. The system may have one or more adapters of the same media type. This will identify the one being used for this link. For example, this is the first (primary) or second (secondary) token-ring adapter." ::= { snaPu20Link802Dot2CfgEntry 7 } snaPu20Link802Dot2CfgAdapterName OBJECT-TYPE SYNTAX DisplayString ACCESS read-write STATUS mandatory DESCRIPTION "Logical name assigned by the user to the underlying adapter." ::= { snaPu20Link802Dot2CfgEntry 8 } -- *************************************************************** -- The following table contains SDLC-specific configuration -- parameters. -- *************************************************************** Expires January 1994 [Page 17] Internet Draft SNANAU MIB July 30, 1993 snaPu20LinkSdlcCfgTable OBJECT-TYPE SYNTAX SEQUENCE OF SnaPu20LinkSdlcCfgEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table contains Managed Objects which describe basic configuration parameters for PUs using SDLC link. The entries in this table can be generated intially, after reboot, by the Agent which uses information from PU configuration file. Subsequent modifications of parameters, creation of new PU link entries and deletion of entries is possible. The modifications of this table can be saved in the PU configuration file for next reboot, but mechanism for this function is not defined here." ::= { snaPu20 3 } snaPu20LinkSdlcCfgEntry OBJECT-TYPE SYNTAX SnaPu20LinkSdlcCfgEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Entry contains all link configuration parameters for one PU. The objects in the entry have read-write access. Entry can be created or deleted. The object snaPu20LinkSdlcCfgEntryStatus is used (set) to create or delete an entry." INDEX { snaPu20LinkSdlcCfgIndex } ::= { snaPu20LinkSdlcCfgTable 1 } SnaPu20LinkSdlcCfgEntry ::= SEQUENCE { snaPu20LinkSdlcCfgIndex INTEGER, snaPu20LinkSdlcCfgAdapterType INTEGER, snaPu20LinkSdlcCfgSourcePort INTEGER, snaPu20LinkSdlcCfgAdapterName DisplayString, snaPu20LinkSdlcCfgDestinationStationAddr OCTET STRING, snaPu20LinkSdlcCfgStationRole INTEGER } Expires January 1994 [Page 18] Internet Draft SNANAU MIB July 30, 1993 snaPu20LinkSdlcCfgIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The index variable assigned by Agent for initial configuration read from file and by Management Station for subsequent entry creation." ::= { snaPu20LinkSdlcCfgEntry 1 } snaPu20LinkSdlcCfgAdapterType OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "Specific network adapter that is used for the SDLC link. The system may have one or more SDLC adapters. This will identify the one being used for this link." ::= { snaPu20LinkSdlcCfgEntry 2 } snaPu20LinkSdlcCfgSourcePort OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The port number being used on this SDLC adapter. This is required for a multi-port adapter." ::= { snaPu20LinkSdlcCfgEntry 3 } snaPu20LinkSdlcCfgAdapterName OBJECT-TYPE SYNTAX DisplayString ACCESS read-write STATUS mandatory DESCRIPTION "Logical name assigned by the user to the underlying adapter." ::= { snaPu20LinkSdlcCfgEntry 4 } snaPu20LinkSdlcCfgDestinationStationAddr OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..1)) ACCESS read-write STATUS mandatory DESCRIPTION Expires January 1994 [Page 19] Internet Draft SNANAU MIB July 30, 1993 "Station Address (1 byte) of the destination node." ::= { snaPu20LinkSdlcCfgEntry 5 } snaPu20LinkSdlcCfgStationRole OBJECT-TYPE SYNTAX INTEGER { secondary (1), primary (2) } ACCESS read-write STATUS mandatory DESCRIPTION "The role of the local station in relation to a remote one." ::= { snaPu20LinkSdlcCfgEntry 6 } -- *************************************************************** -- The following table contains QLLC specific configuration -- parameters. -- *************************************************************** snaPu20LinkQllcCfgTable OBJECT-TYPE SYNTAX SEQUENCE OF SnaPu20LinkQllcCfgEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table contains Managed Objects which describe basic configuration parameters for PUs using QLLC link. The entries in this table can be generated intially, after reboot, by the Agent which uses information from PU configuration file. Subsequent modifications of parameters, creation of new PU link entries and deletion of entries is possible. The modifications of this table can be saved in the PU configuration file for next reboot, but mechanism for this function is not defined here." ::= { snaPu20 4 } snaPu20LinkQllcCfgEntry OBJECT-TYPE SYNTAX SnaPu20LinkQllcCfgEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Entry contains all link configuration parameters Expires January 1994 [Page 20] Internet Draft SNANAU MIB July 30, 1993 for one PU. The objects in the entry have read-write access. Entry can be created or deleted. The object snaPu20LinkQllcCfgEntryStatus is used (set) to create or delete an entry." INDEX { snaPu20LinkQllcCfgIndex } ::= { snaPu20LinkQllcCfgTable 1 } SnaPu20LinkQllcCfgEntry ::= SEQUENCE { snaPu20LinkQllcCfgIndex PositiveInteger, snaPu20LinkQllcCfgAdapterName DisplayString, snaPu20LinkQllcCfgPort INTEGER, snaPu20LinkQllcCfgLcn INTEGER, snaPu20LinkQllcCfgSourceDteAddr OCTET STRING, snaPu20LinkQllcCfgDestinationDteAddr OCTET STRING, snaPu20LinkQllcCfgFacilities OCTET STRING, snaPu20LinkQllcCfgUserData OCTET STRING } snaPu20LinkQllcCfgIndex OBJECT-TYPE SYNTAX PositiveInteger ACCESS read-only STATUS mandatory DESCRIPTION "The index variable assigned by Agent for initial configuration read from file and by Management Station for subsequent entry creation." ::= { snaPu20LinkQllcCfgEntry 1 } snaPu20LinkQllcCfgAdapterName OBJECT-TYPE SYNTAX DisplayString ACCESS read-write STATUS mandatory DESCRIPTION "Logical name assigned by the user to the underlying adapter." ::= { snaPu20LinkQllcCfgEntry 2 } Expires January 1994 [Page 21] Internet Draft SNANAU MIB July 30, 1993 snaPu20LinkQllcCfgPort OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The port number being used on this X.25 adapter. This is required for a multi-port adapter." ::= { snaPu20LinkQllcCfgEntry 3 } snaPu20LinkQllcCfgLcn OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "The Logical Channel Number (LCN) used by the source node in the case of SVC. Identifies the Circuit number in the case of PVC." ::= { snaPu20LinkQllcCfgEntry 4 } snaPu20LinkQllcCfgSourceDteAddr OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..15)) ACCESS read-write STATUS mandatory DESCRIPTION "The DTE Address (15 bytes) of the source node." ::= { snaPu20LinkQllcCfgEntry 5 } snaPu20LinkQllcCfgDestinationDteAddr OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..15)) ACCESS read-write STATUS mandatory DESCRIPTION "The DTE Address (15 bytes) of the destination node." ::= { snaPu20LinkQllcCfgEntry 6 } snaPu20LinkQllcCfgFacilities OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-write STATUS mandatory DESCRIPTION "The facilities field used to establish Expires January 1994 [Page 22] Internet Draft SNANAU MIB July 30, 1993 the x.25 link." ::= { snaPu20LinkQllcCfgEntry 7 } snaPu20LinkQllcCfgUserData OBJECT-TYPE SYNTAX OCTET STRING ACCESS read-write STATUS mandatory DESCRIPTION "The user data field used to establish the x.25 link." ::= { snaPu20LinkQllcCfgEntry 8 } -- *************************************************************** -- The following table contains PU status dynamic parameters. -- *************************************************************** snaPu20StateTable OBJECT-TYPE SYNTAX SEQUENCE OF SnaPu20StateEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table contains the dynamic parameters which have read-only access. There is also one control parameter snaPu20StateAdminState which has read-write access. The enrties in this table augment the entries in the snaPu20CfgTable and cannot be created by Management Station." ::= { snaPu20 5 } snaPu20StateEntry OBJECT-TYPE SYNTAX SnaPu20StateEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The entry contains parameters which describe the state of one PU. They have read-only access. Each configured PU from snaPu20CfgTable (valid entry) has one entry in this table and the index used here has the same values as snaPu20CfgIndex of that PU. The entry is created by the Agent. The variable snaPu20StateAdminState has read-write access and is used to start or stop the PU." INDEX { snaPu20StateIndex } ::= { snaPu20StateTable 1 } Expires January 1994 [Page 23] Internet Draft SNANAU MIB July 30, 1993 SnaPu20StateEntry ::= SEQUENCE { snaPu20StateIndex PositiveInteger, snaPu20StateOperState OperState, snaPu20StateAdminState AdminState, snaPu20StateHostSscpId OCTET STRING, snaPu20StateStartTime TimeTicks, snaPu20StateLastStateChange TimeTicks, snaPu20StateActFailureReason INTEGER, snaPu20StateLinkStateSpecific OBJECT IDENTIFIER } snaPu20StateIndex OBJECT-TYPE SYNTAX PositiveInteger ACCESS read-only STATUS mandatory DESCRIPTION "The instance of the entry parameters. The index value is taken by the Agent from snaPu20CfgIndex." ::= { snaPu20StateEntry 1 } snaPu20StateOperState OBJECT-TYPE SYNTAX OperState ACCESS read-only STATUS mandatory DESCRIPTION "The operational state of the PU." ::= { snaPu20StateEntry 2 } snaPu20StateAdminState OBJECT-TYPE SYNTAX AdminState ACCESS read-write STATUS mandatory DESCRIPTION "The administrative state of the PU and is used by Management Station to start or stop the PU. The values that can be read and written Expires January 1994 [Page 24] Internet Draft SNANAU MIB July 30, 1993 are: start (2) - this value has to be used to start, stop (3) - this value has to be used to stop. The values that can be read only are: other (1) - this value indicates that the variable has not been set after reboot." ::= { snaPu20StateEntry 3 } snaPu20StateHostSscpId OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..6)) ACCESS read-only STATUS mandatory DESCRIPTION "The SSCP Id from the activation." ::= { snaPu20StateEntry 4 } snaPu20StateStartTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "The time stamp of the PU activation." ::= { snaPu20StateEntry 5 } snaPu20StateLastStateChange OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "The time stamp of the last state change of the PU." ::= { snaPu20StateEntry 6 } snaPu20StateActFailureReason OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The sense code for the activation failure. It will be sent in the trap snaPu20ActFailTrap." ::= { snaPu20StateEntry 7 } snaPu20StateLinkStateSpecific OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-only Expires January 1994 [Page 25] Internet Draft SNANAU MIB July 30, 1993 STATUS mandatory DESCRIPTION "The reference to the index object in the table which contains the link specific status information." ::= { snaPu20StateEntry 8 } -- *************************************************************** -- The following table contains PU statistics dynamic parameters. -- *************************************************************** snaPu20StatsTable OBJECT-TYPE SYNTAX SEQUENCE OF SnaPu20StatsEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table contains the dynamic parameters which have read-only access. The entries in this table augment the entries in the snaPu20CfgTable and cannot be created by Management Station." ::= { snaPu20 6 } snaPu20StatsEntry OBJECT-TYPE SYNTAX SnaPu20StatsEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The entry contains parameters which describe the state of one PU. They have read-only access. Each configured PU from snaPu20CfgTable (valid entry) has one entry in this table and the index used here has the same values as snaPu20CfgIndex of that PU. The entry is created by the Agent." INDEX { snaPu20StatsIndex } ::= { snaPu20StatsTable 1 } SnaPu20StatsEntry ::= SEQUENCE { snaPu20StatsIndex PositiveInteger, snaPu20StatsBytesSent Counter, snaPu20StatsBytesReceived Counter, snaPu20StatsRuSent Expires January 1994 [Page 26] Internet Draft SNANAU MIB July 30, 1993 Counter, snaPu20StatsRuReceived Counter, snaPu20StatsNegativeRespSent Counter, snaPu20StatsActiveLu Gauge, snaPu20StatsActLu Gauge, snaPu20StatsInActLu Gauge, snaPu20StatsBindLu Gauge, snaPu20StatsPeakBindLu INTEGER } snaPu20StatsIndex OBJECT-TYPE SYNTAX PositiveInteger ACCESS read-only STATUS mandatory DESCRIPTION "The instance of the entry parameters. The index value is taken by the Agent from snaPu20CfgIndex." ::= { snaPu20StatsEntry 1 } snaPu20StatsBytesSent OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of bytes sent by PU." ::= { snaPu20StatsEntry 2 } snaPu20StatsBytesReceived OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of bytes received by PU." ::= { snaPu20StatsEntry 3 } snaPu20StatsRuSent OBJECT-TYPE SYNTAX Counter Expires January 1994 [Page 27] Internet Draft SNANAU MIB July 30, 1993 ACCESS read-only STATUS mandatory DESCRIPTION "The number of RUs sent by PU." ::= { snaPu20StatsEntry 4 } snaPu20StatsRuReceived OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of RUs received by PU." ::= { snaPu20StatsEntry 5 } snaPu20StatsNegativeRespSent OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of negative responses sent by PU." ::= { snaPu20StatsEntry 6 } snaPu20StatsActiveLu OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION "The number of LUs currently active on this PU." ::= { snaPu20StatsEntry 7 } snaPu20StatsActLu OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION "The number of LUs on this PU which have received and responded to ACTLU from the host." ::= { snaPu20StatsEntry 8 } snaPu20StatsInActLu OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory Expires January 1994 [Page 28] Internet Draft SNANAU MIB July 30, 1993 DESCRIPTION "The number of LUs on this PU which have not received an ACTLU from the host. This is possible if the number of configured LUs exceeds that on the host." ::= { snaPu20StatsEntry 9 } snaPu20StatsBindLu OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION "The number of LUs on this PU which have received and acknowledged a BIND request from the host." ::= { snaPu20StatsEntry 10 } snaPu20StatsPeakBindLu OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The highest number of bound LUs on this PU from the time this PU is activated." ::= { snaPu20StatsEntry 11 } -- *************************************************************** -- Traps -- *************************************************************** snaPu20Trap OBJECT IDENTIFIER ::= { snaPu20 0 } snaPu20StateChangeTrap TRAP-TYPE ENTERPRISE snaPu20Trap VARIABLES { snaPu20StateOperState } -- STATUS mandatory DESCRIPTION "The operational state of a PU has changed. The following variable are returned: snaPu20StateOperState...the current state after the change, with the instance identifying the PU." ::= 0 Expires January 1994 [Page 29] Internet Draft SNANAU MIB July 30, 1993 snaPu20ActFailTrap TRAP-TYPE ENTERPRISE snaPu20Trap VARIABLES { snaPu20StateOperState, snaPu20StateActFailureReason } -- STATUS mandatory DESCRIPTION "The trap sent to indicate the failure of ACT. Value snaPu20StateOperState indicates the current state after change. Value snaPu20StateActFailureReason indicates the failure reason." ::= 1 -- *************************************************************** -- snaLu group -- -- Implementation of the snaLu group is mandatory. -- -- It contains Managed Objects for LUs of types 0, 1, 2, 3. -- *************************************************************** snaLuCfgTable OBJECT-TYPE SYNTAX SEQUENCE OF SnaLuCfgEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table of LUs' (0, 1, 2, 3) configuration information." ::= { snaLu 1 } snaLuCfgEntry OBJECT-TYPE SYNTAX SnaLuCfgEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Contains configuration variables of an LU of type 0, 1, 2 or 3." INDEX { snaLuCfgPuIndex, snaLuCfgLuIndex } ::= { snaLuCfgTable 1 } SnaLuCfgEntry ::= SEQUENCE { snaLuCfgPuIndex INTEGER, snaLuCfgLuIndex Expires January 1994 [Page 30] Internet Draft SNANAU MIB July 30, 1993 INTEGER, snaLuCfgName DisplayString, snaLuCfgVtamName DisplayString, snaLuCfgType INTEGER, snaLuCfgDisplayModel INTEGER, snaLuCfgPoolName DisplayString } snaLuCfgPuIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Index in the snaPu20CfgTable of the PU 2.0 with which this LU is associated." ::= { snaLuCfgEntry 1 } snaLuCfgLuIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Unique index of an LU in a PU 2.0." ::= { snaLuCfgEntry 2 } snaLuCfgName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..512)) ACCESS read-write STATUS mandatory DESCRIPTION "User configurable name for this LU. May be a zero length string if not assigned." ::= { snaLuCfgEntry 3 } snaLuCfgVtamName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..8)) ACCESS read-only STATUS mandatory DESCRIPTION "VTAM name for this LU. May be a zero Expires January 1994 [Page 31] Internet Draft SNANAU MIB July 30, 1993 length string." ::= { snaLuCfgEntry 4 } snaLuCfgType OBJECT-TYPE SYNTAX INTEGER { lu0(1), lu1(2), lu2(3), lu3(4) } ACCESS read-only STATUS mandatory DESCRIPTION "Identifies whether the LU is Type 0, 1, 2 or 3." ::= { snaLuCfgEntry 5 } snaLuCfgDisplayModel OBJECT-TYPE SYNTAX INTEGER { invalid(1), model2(2), model3(3), model4(4), model5(5) } ACCESS read-only STATUS mandatory DESCRIPTION "The screen model type of the terminal connected to the host. This is only valid for LU Type 2. In case this LU is not Type 2, then this object should contain the invalid(1) value." ::= { snaLuCfgEntry 6 } snaLuCfgPoolName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..16)) ACCESS read-write STATUS mandatory DESCRIPTION "The name of the LU pool to which this LU belongs. An LU Pool is configured by the user. It contains a group of LUs any of which can be assigned to an user requesting an LU by the Pool name. May be a zero length string if this LU does not belong to a pool, or if a gateway vendor does not Expires January 1994 [Page 32] Internet Draft SNANAU MIB July 30, 1993 support the concept of LU Pooling." ::= { snaLuCfgEntry 7 } -- *************************************************************** -- The following table contains LU state dynamic parameters. -- *************************************************************** snaLuStateTable OBJECT-TYPE SYNTAX SEQUENCE OF SnaLuStateEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table containing dynamic runtime information and control variables relating to an LU (Type 0, 1, 2 or 3). The entries in this table augment the entries in the snaLuCfgTable." ::= { snaLu 2 } snaLuStateEntry OBJECT-TYPE SYNTAX SnaLuStateEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Contains state and control variables as well as user information of an LU (Type 0, 1, 2 or 3). Each entry is created by the agent. All entries have read-only access except snaLuStateReset which is used to reset an LU. Each configured LU from snaLuCfgTable (valid entry) has one entry in this table and the indexes used here have the same values as snaLuCfgPuIndex and snaLuCfgIndex." INDEX { snaLuStatePuIndex, snaLuStateLuIndex } ::= { snaLuStateTable 1 } SnaLuStateEntry ::= SEQUENCE { snaLuStatePuIndex INTEGER, snaLuStateLuIndex INTEGER, snaLuStateCurrentState INTEGER, snaLuStateReset INTEGER, Expires January 1994 [Page 33] Internet Draft SNANAU MIB July 30, 1993 snaLuStateLastResetTime TimeTicks, snaLuStateLocalApplName DisplayString, snaLuStatePluName DisplayString, snaLuStateActiveTime TimeTicks, snaLuStateBindTime TimeTicks, snaLuStateBindFailureReason INTEGER } snaLuStatePuIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Identifies the PU 2.0 with which this LU is associated." ::= { snaLuStateEntry 1 } snaLuStateLuIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Unique index of an LU in a PU 2.0." ::= { snaLuStateEntry 2 } snaLuStateCurrentState OBJECT-TYPE SYNTAX INTEGER { inactive(1), active(2), bound(3) } ACCESS read-only STATUS mandatory DESCRIPTION "The current operational state of this LU: whether it is inactive, active (ACTLU received and acked), or bound (BIND received and acked)." ::= { snaLuStateEntry 3 } Expires January 1994 [Page 34] Internet Draft SNANAU MIB July 30, 1993 snaLuStateReset OBJECT-TYPE SYNTAX INTEGER { noAction(1), reset(2) } ACCESS read-only STATUS mandatory DESCRIPTION "This object is used by a management station to initiate an LU reset request. This results in the LU state becoming inactive." ::= { snaLuStateEntry 4 } snaLuStateLastResetTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "Time stamp when this LU was last reset." ::= { snaLuStateEntry 5 } snaLuStateLocalApplName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..512)) ACCESS read-only STATUS mandatory DESCRIPTION "The name of the local application using this LU. May be a zero length string if local application not known." ::= { snaLuStateEntry 6 } snaLuStatePluName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..8)) ACCESS read-only STATUS mandatory DESCRIPTION "The name of the host application (Primary LU) the LU is bound to. It may be a zero length string if the LU is not bound or the host application name is not available." ::= { snaLuStateEntry 7 } snaLuStateActiveTime OBJECT-TYPE SYNTAX TimeTicks Expires January 1994 [Page 35] Internet Draft SNANAU MIB July 30, 1993 ACCESS read-only STATUS mandatory DESCRIPTION "The time stamp when this LU becomes active." ::= { snaLuStateEntry 8 } snaLuStateBindTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "The time stamp when this LU was bound." ::= { snaLuStateEntry 9 } snaLuStateBindFailureReason OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The sense code when there is a bind failure." ::= { snaLuStateEntry 10 } -- *************************************************************** -- The following table contains LU statistics dynamic parameters. -- *************************************************************** snaLuStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF SnaLuStatsEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table containing dynamic statistics information relating to an LU (Type 0, 1, 2 or 3). The entries in this table augment the entries in the snaLuCfgTable and cannot be created by a Management Station." ::= { snaLu 3 } snaLuStatsEntry OBJECT-TYPE SYNTAX SnaLuStatsEntry ACCESS not-accessible STATUS mandatory DESCRIPTION Expires January 1994 [Page 36] Internet Draft SNANAU MIB July 30, 1993 "Contains statistics information of an LU (Type 0, 1, 2 or 3). Each entry is created by the agent. Objects in this table have read-only access. Each configured LU from snaLuCfgTable (valid entry) has one entry in this table and the indexes used here have the same values as snaLuCfgPuIndex and snaLuCfgIndex." INDEX { snaLuStatsPuIndex, snaLuStatsLuIndex } ::= { snaLuStatsTable 1 } SnaLuStatsEntry ::= SEQUENCE { snaLuStatsPuIndex INTEGER, snaLuStatsLuIndex INTEGER, snaLuStatsBytesSent Counter, snaLuStatsBytesReceived Counter, snaLuStatsRuSent Counter, snaLuStatsRuReceived Counter, snaLuStatsNegativeRuSent Counter } snaLuStatsPuIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Identifies the PU 2.0 with which this LU is associated." ::= { snaLuStatsEntry 1 } snaLuStatsLuIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Uniquely identifies an LU in a PU 2.0." ::= { snaLuStatsEntry 2 } snaLuStatsBytesSent OBJECT-TYPE Expires January 1994 [Page 37] Internet Draft SNANAU MIB July 30, 1993 SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of bytes sent by the local LU." ::= { snaLuStatsEntry 3 } snaLuStatsBytesReceived OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of bytes received by the local LU." ::= { snaLuStatsEntry 4 } snaLuStatsRuSent OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of RUs sent by the local LU." ::= { snaLuStatsEntry 5 } snaLuStatsRuReceived OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of RUs received by the local LU." ::= { snaLuStatsEntry 6 } snaLuStatsNegativeRuSent OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of negative RUs sent by the local LU." ::= { snaLuStatsEntry 7 } -- *************************************************************** -- Traps -- *************************************************************** snaLuTrap OBJECT IDENTIFIER ::= { snaLu 0 } Expires January 1994 [Page 38] Internet Draft SNANAU MIB July 30, 1993 snaLuStateChangeTrap TRAP-TYPE ENTERPRISE snaLuTrap VARIABLES { snaLuStateCurrentState } -- STATUS mandatory DESCRIPTION "The operational state of the LU has changed. Value snaLuStateCurrentState indicates the current state after change." ::= 0 snaLuBindFailTrap TRAP-TYPE ENTERPRISE snaLuTrap VARIABLES { snaLuStateCurrentState, snaLuStateBindFailureReason } -- STATUS mandatory DESCRIPTION "The trap sent to indicate the failure of BIND. Value snaLuStateCurrentState indicates the current state after change. Value snaLuStateBindFailureReason indicates the failure reason." ::= 1 -- *************************************************************** -- snaMgtTools group -- -- Implementation of the snaMgtTools group is optional. -- -- Currently this group contains only one table. -- The following table contains RTM statistics for LU 2. -- *************************************************************** snaLuRtmTable OBJECT-TYPE SYNTAX SEQUENCE OF SnaLuRtmEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "Table containing RTM information relating to an LU (Type 2)." ::= { snaMgtTools 1 } snaLuRtmEntry OBJECT-TYPE SYNTAX SnaLuRtmEntry Expires January 1994 [Page 39] Internet Draft SNANAU MIB July 30, 1993 ACCESS not-accessible STATUS mandatory DESCRIPTION "Contains RTM information for an LU (Type 2). Each entry is created by the agent." INDEX { snaLuRtmPuIndex, snaLuRtmLuIndex } ::= { snaLuRtmTable 1 } SnaLuRtmEntry ::= SEQUENCE { snaLuRtmPuIndex INTEGER, snaLuRtmLuIndex INTEGER, snaLuRtmRequest INTEGER, snaLuRtmState INTEGER, snaLuRtmDef INTEGER, snaLuRtmBoundary1 INTEGER, snaLuRtmBoundary2 INTEGER, snaLuRtmBoundary3 INTEGER, snaLuRtmBoundary4 INTEGER, snaLuRtmCounter1 Counter, snaLuRtmCounter2 Counter, snaLuRtmCounter3 Counter, snaLuRtmCounter4 Counter, snaLuRtmOverFlow Counter, snaLuRtmObjective INTEGER, snaLuRtmActual INTEGER, snaLuRtmNumTrans INTEGER, snaLuRtmLastRspTime INTEGER, Expires January 1994 [Page 40] Internet Draft SNANAU MIB July 30, 1993 snaLuRtmAvgRspTime INTEGER } snaLuRtmPuIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Identifies the PU 2.0 with which this LU is associated." ::= { snaLuRtmEntry 1 } snaLuRtmLuIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Uniquely identifies an LU in a PU 2.0." ::= { snaLuRtmEntry 2 } snaLuRtmRequest OBJECT-TYPE SYNTAX INTEGER { off(1), on(2) } ACCESS read-only STATUS mandatory DESCRIPTION "This object is used by a management station to initiate or cancel an RTM request." ::= { snaLuRtmEntry 3 } snaLuRtmState OBJECT-TYPE SYNTAX INTEGER { off(1), on(2) } ACCESS read-only STATUS mandatory DESCRIPTION "The current RTM state of an LU." ::= { snaLuRtmEntry 4 } snaLuRtmDef OBJECT-TYPE Expires January 1994 [Page 41] Internet Draft SNANAU MIB July 30, 1993 SYNTAX INTEGER { firstChar(1), kb(2), cdeb(3) } ACCESS read-only STATUS mandatory DESCRIPTION "The mode of measurement of this RTM request. The values have following meaning: firstChar(1) - time to first character on screen kb(2) - time to keyboard usable by operator cdeb(3) - time to Change Direction/End Bracket." ::= { snaLuRtmEntry 5 } snaLuRtmBoundary1 OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The value of the first boundary in minutes and seconds." ::= { snaLuRtmEntry 6 } snaLuRtmBoundary2 OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The value of the second boundary in minutes and seconds." ::= { snaLuRtmEntry 7 } snaLuRtmBoundary3 OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The value of the third boundary in minutes and seconds." ::= { snaLuRtmEntry 8 } snaLuRtmBoundary4 OBJECT-TYPE SYNTAX INTEGER ACCESS read-only Expires January 1994 [Page 42] Internet Draft SNANAU MIB July 30, 1993 STATUS mandatory DESCRIPTION "The value of the fourth boundary in minutes and seconds." ::= { snaLuRtmEntry 9 } snaLuRtmCounter1 OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of transactions which fall in the range specified by the first boundary." ::= { snaLuRtmEntry 10 } snaLuRtmCounter2 OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of transactions which fall in the range specified by the second boundary." ::= { snaLuRtmEntry 11 } snaLuRtmCounter3 OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of transactions which fall in the range specified by the third boundary." ::= { snaLuRtmEntry 12 } snaLuRtmCounter4 OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The number of transactions which fall in the range specified by the fourth boundary." ::= { snaLuRtmEntry 13 } snaLuRtmOverFlow OBJECT-TYPE SYNTAX Counter ACCESS read-only Expires January 1994 [Page 43] Internet Draft SNANAU MIB July 30, 1993 STATUS mandatory DESCRIPTION "The number of transactions which exceed the highest range specified by the boundaries." ::= { snaLuRtmEntry 14 } snaLuRtmObjective OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The desired percentage of transactions which should be under a designated boundary range." ::= { snaLuRtmEntry 15 } snaLuRtmActual OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The actual percentage of transactions which are under a designated boundary range." ::= { snaLuRtmEntry 16 } snaLuRtmNumTrans OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The total number of transactions executed during this period." ::= { snaLuRtmEntry 17 } snaLuRtmLastRspTime OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The response time for the last transaction." ::= { snaLuRtmEntry 18 } snaLuRtmAvgRspTime OBJECT-TYPE Expires January 1994 [Page 44] Internet Draft SNANAU MIB July 30, 1993 SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The average response time for all transactions." ::= { snaLuRtmEntry 19 } END Expires January 1994 [Page 45] Internet Draft SNANAU MIB July 30, 1993 7. Acknowledgments Special thanks goes to Dave Perkins for his assistance in reviewing this MIB proposal. Expires January 1994 [Page 46] Internet Draft SNANAU MIB July 30, 1993 8. References [1] Cerf, V., "IAB Recommendations for the Development of Internet Network Management Standards", RFC 1052, NRI, April 1988. [2] Cerf, V., "Report of the Second Ad Hoc Network Management Review Group", RFC 1109, NRI, August 1989. [3] Rose M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based internets", RFC 1155, Performance Systems International, Hughes LAN Systems, May 1990. [4] McCloghrie K., and M. Rose, "Management Information Base for Network Management of TCP/IP-based internets", RFC 1156, Hughes LAN Systems, Performance Systems International, May 1990. [5] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", RFC 1157, SNMP Research, Performance Systems International, Performance Systems International, MIT Laboratory for Computer Science, May 1990. [6] McCloghrie K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets", RFC 1213, Performance Systems International, March 1991. [7] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization, International Standard 8824, December 1987. [8] Information processing systems - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Notation One (ASN.1), International Organization for Standardization, International Standard 8825, December 1987. [9] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions" , RFC 1212, Performance Systems International, Hughes LAN Systems, March 1991. Expires January 1994 [Page 47] Internet Draft SNANAU MIB July 30, 1993 9. Security Considerations Security issues are not discussed in this memo. 10. Authors' Addresses Zbigniew Kielczewski (editor) Eicon Technology Corporation 2196 32nd Avenue Montreal, Quebec, Canada H8T 3H7 zbig@eicon.qc.ca Kitty Shih (editor) Novell 890 Ross Drive Sunnyvale, CA 94089 kmshih@novell.com Expires January 1994 [Page 48] Internet Draft SNANAU MIB July 30, 1993 Table of Contents 1 Status of this Memo ................................... 1 2 Abstract .............................................. 2 3 The Network Management Framework ...................... 3 4 Objects ............................................... 4 4.1 Format of Definitions ............................... 4 5 Overview .............................................. 5 5.1 Applying MIB II to managing SNA NAUs ................ 5 5.2 SNANAU MIB Structure ................................ 6 5.2.1 SNA PU 2.0 (snaPu20) Group ........................ 6 5.2.2 SNA LU (snaLu) Group .............................. 7 5.2.3 SNA Management Tools (snaMgtTools) Group .......... 7 6 Object Definitions .................................... 8 7 Acknowledgments ....................................... 46 8 References ............................................ 47 9 Security Considerations ............................... 48 10 Authors' Addresses ................................... 48 Expires January 1994 [Page 49]